home *** CD-ROM | disk | FTP | other *** search
Text File | 1989-11-10 | 1.8 KB | 42 lines | [TEXT/GEOL] |
- Item forwarded by A33 to A34
-
- Item forwarded by MUSIC.MAN to MOHAN.801
-
- Item 7255293 7-Nov-89 06:16
-
- From: SCHMUCKER1 Schmucker, Kurt
-
- To: MACAPP.TECH$ MacApp Technical
-
- cc: COMMENTS -> ASK.HELPLINE Comments
- ALINK.BUGS -> MUSIC.MAN AppleLink bug reporting
-
- Sub: Multiple Transmisstions
-
- To all the MacApp.Tech readers:
-
- There has been a real rash of multiple transmissions lately. Most
- probably, the senders are NOT at fault. The problem is AppleLink and the
- algorithms it uses when a link is sent to a group address like MacApp.Tech$.
- Basically, instead of queueing the link, and "sending" it to all the names in
- the group address later, AppleLink tries to send the link to all the names
- WHILE THE SENDER IS CONNECTED and transmitting.
-
- Usually this doesn't matter too much, but MacApp.Tech$ is the largest group
- address on AppleLink. Thus if you are sending your link to such a large group
- during peak times, it is possible to "time out" during the transmission. Since
- your Mac did not get acknowledgement that the message was correctly sent to
- MacApp.Tech$, it is left in your out-basket. When you later log on, you think
- that the message never got sent. In reality, it may have been sent to 95% of
- MacApp.Tech$. You re-transmit and then that 95% gets a second copy.
-
- Admittedly, the problem is Applelink's and they should fix it. However,
- until they do, here is a work-around that I have used successfully: Batch your
- links to MacApp.Tech and transmit them at off-peak hours: e.g., before 8am
- (PST) and after 6 pm (PST). It is a little bit of trouble, but think how you
- will be helping cut down on the MacApp.Tech deluge.
-
-
- Kurt
-
-